|
IBM Integration Bus (formerly known as WebSphere Message Broker) is IBM's integration broker from the WebSphere product family that allows business information to flow between disparate applications across multiple hardware and software platforms. Rules can be applied to the data flowing through the message broker to route and transform the information. The product is an Enterprise Service Bus supplying a communication channel between applications and services in a service-oriented architecture. IBM Integration Bus provides capabilities to build solutions needed to support diverse integration requirements through a set of connectors to a range of data sources, including packaged applications, files, mobile devices, messaging systems, and databases. A benefit of using IBM Integration Bus is that the tool enables existing applications for Web Services without costly legacy application rewrites. IIB (IBM Integration Bus) avoids the point-to-point strain on development resources by connecting any application or service over multiple protocols, including SOAP, HTTP and JMS.〔http://public.dhe.ibm.com/common/ssi/ecm/en/wss14112usen/WSS14112USEN.PDF〕 Modern secure authentication mechanisms, including the ability to perform actions on behalf of masquerading or delegate users, through MQ, HTTP and SOAP nodes are supported such as LDAP, X-AUTH, O-AUTH, and two-way SSL. IBM Integration Bus embeds a Common Language Runtime to invoke any .NET logic as part of an integration. It also includes full support for the Visual Studio development environment, including the integrated debugger and code templates. IBM Integration Bus includes a comprehensive set of patterns and samples that demonstrate bi-directional connectivity with both Microsoft Dynamics CRM and MSMQ. ==Features== IBM represents the following features as key differentiators of the IIB product when compared to other industry products that provide the services of an Enterprise Service Bus: * Simplicity and productivity * * Simplified process for installation : The process to deploy and configure IBM Integration Bus so that an integration developer can use the IBM Integration Toolkit to start creating applications is simplified and quicker to complete. * * Tutorials Gallery : From the Tutorials Gallery you can download, deploy, and test sample integration solutions. * * Shared libraries : Shared libraries are introduced in V10 to share resources between multiple applications. Libraries in previous versions of IBM Integration Bus are static libraries. * * Removal of the WebSphere MQ prerequisite : WebSphere MQ is no longer a prerequisite for using IBM Integration Bus on distributed platforms, which means that you can develop and deploy applications independently of WebSphere MQ. * Universal and independent * Graphical data mapping * Industry-specific and relevant * Dynamic and intelligent * High-performing and scalable IBM delivers the IIB software either in traditional software install on your local premises or by an IBM administered cloud environment. The Integration Bus in a cloud environment reduces capital expenditures, increases application and hardware availability, and offloads the skills for managing an Integration Bus environment to IBM cloud engineers. This promotes the ability of end users to focus on developing solutions rather than installing, configuring, and managing the IIB software. The offering is intended to be compatible with the on-premises product. Within the constraints of a cloud environment, users can use the same development tooling for both cloud and on-premises software, and the assets that are generated can be deployed to either. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「IBM Integration Bus」の詳細全文を読む スポンサード リンク
|